

Remember-Things we should never forget

Nothing new but in greater detail
a reader's reviewThis book was published as a well bound, hardback, dust jacketed book by Aegean Park Press, a publishing house well known for re-printing (keeping available and alive) important Cryptanalytical, Cryptological, Cryptograhic publications in softcover 8-1/2" x 11" format. Just the way this particular publishing house, who specializes in crypto works is treating this book "screams" the high regard they have for it.
If you're looking for crypto course work, the how-to-do-it, Aegean Park Press has it, (though not in this book). If you are looking for the taste and feel, the heart and soul of real cryptanalysts enjoying their work, that IS the form & substance of this book; as well as being an important historical work.
A fascinating book on World War II secert communications.

Not for developers (designers & programmers)
A book worth buying if you have patienceThe book uses UML for all diagrams. It explores different options that the software architect can choose from depending on the type of project and the comfortability level. For eg., the author explains the usage of state machines, decision tables and sequence diagrams during the Analysis phase of a system. Any of these processes can be used by the reader. It explains the logic behind constructing class diagrams from use cases, how to establish relation between classes and deriving the database table structures from classes. It lays emphasis on testing the finished product and how to go cover different test cases .
The book does include some case studies which many readers might find helpful and use them as "templates" in tackling their projects.
I have done two projects using this book and have been able to bang in the time estimates. Also it has helped me in the actual coding much easier.
In a nutshell, I would give a good rating to this book since it has really helped me to get into the Object Oriented world of programming and develop into a much better and efficient programmer.
Good book to start out if shifting from mainframeThe book has chapters on requirements definition, analysis, use case design, class design, persistence,implementation, testing, user interface, maintenance, project management and over 100 pages dedicated to a case study with 4 increments (very detailed and helpful).
The book uses UML diagrams as examples and touches upon subjects such as the importance of correctness, of having a data dictionary, planning, and it has a good summary and glossary at the end. It even gives an example on how to build an estimating model spreadsheet using metrics and statistical correlation.
One topic that is missing is security and how it fits into applications. Also, the chapter on requirements definition is a little weak since it blends into use cases right away and does not give the reader a clear message on how to reduce ambiguity, what a requirements specification should contain, etc. But there are good books on requirements that can be bought.
Overall a really good book that can help any manager or developer with getting started using OO concepts.


Poor
Good Overview of the Case
Absorbing look at shocking crime

Much Discernment Required



